Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference
653-tree-1
name
1699
tree-preservation-order

undefined

653-tpo-1
uprn
address-text
point
POINT (-1.006640 50.863654)
geometry
MULTIPOLYGON (((-1.006499 50.863639,-1.006505 50.863667,-1.006525 50.863692,-1.006556 50.863713,-1.006595 50.863726,-1.006639 50.863730,-1.006683 50.863726,-1.006723 50.863714,-1.006754 50.863694,-1.006775 50.863669,-1.006783 50.863642,-1.006776 50.863614,-1.006757 50.863589,-1.006726 50.863568,-1.006686 50.863555,-1.006643 50.863551,-1.006599 50.863555,-1.006559 50.863567,-1.006527 50.863587,-1.006506 50.863612,-1.006499 50.863639)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL